#Github repo

[bloodpraxis]

I finished coding my Rogue Trader character sheet template! It's now open sourced on GitHub 🤖

☆ Features

Display your character's stats in (almost) the same way as you've seen in Warhammer 40,000: Rogue Trader CRPG

Multiple sections for character building:

Summary: Character origin info, alignment level, history, and biography.

Features: Show off your build by listing abilities & talents that your character has gained throughout the course of the game.

Inventory: Your Rogue Trader's equipment, armour, etc. goes here.

Relations: Detail the relationship of your Rogue Trader and their retinue members.

Gallery: Place to show off your fanart, commissioned art, fanfics, playlist. Anything goes!

Cool floating servo skulls (only visible in certain screen sizes).

Responsive. Not horrible to look at even in small screens.

☆ Requirements

You would need a static site hosting service for this to work. I recommend Neocities or GitHub pages. Both are free.

Some experience with using npm.

Some experience with basic HTML and JS object/JSON is recommended.

I really wish that it's easier to use and set up, but it's just not possible due to the tech stack I chose initially... I did write a beginner's tutorial on the repository's wiki, but I don't know if it makes sense to normal people who do not code... If you have any questions, let me know and I'll see what I can do.

Tech stack: SvelteKit, SCSS, TypeScript

Bonus:

Name too long? No problem :)

[froget-me-nots]

deskpet mikey :)

[snarp]

Hiii sorry if this is a bother, but is there somewhere to access the Japanese script/item descriptions for the game?

Base game text dump:

Shadow of the Erdtree DLC text dump:

Also these:

* Carian-Archive-Global - languages other than English and Japanese (no DLC content)

* Elden Ring Text Explorer - try this if you're having trouble figuring out how to use Carian-Archive (but note that it can be glitchy on mobile devices, slow connections, etc) (no DLC content)

[tsvai]

my github repo commit history is a clownshow

[dkettchen]

I've learnt how to input in python I will be unstoppable now

[mfcl3780cdw]

i have just as much webdev experience as i have IT experience but that world feels so much more alien sometimes.

average reddit post about web development: "yeah to build my website i just use [lists 15 different frameworks and tools that cost hundreds of dollars per license]"

every team i've worked with:

[incirrata]

git HATES letting you remove files from repositories. oops that file is too big to push to github guess I'll not only add it to .gitignore but also reset my last 7 commits since I made it move it out of the folder and then recommit all my changes. please somebody tell me there's a better way to do this that I didn't find on stack overflow.

[foxelfire]

putting my first programming project out into the world, absolutely terrified

why is this so suspensefulllllll

[transienturl]

6. Contributions Under Repository License Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit.

I guess that—and I can't imagine that this comes up much—if you make a pull request to a repository, and then the license on that repository is changed, you have only licensed your contribution under the old license (and it might not be mergable) until your permission is sought out to update the license under which you're making the contribution.

(also, I was thinking about a scenario in which you make a fork and then someone else makes a pull request from one of your branches to the upstream repo without your permission; presumably in that case the person making the pull request is the one in violation of any copyright/licensing/terms that may apply, hence the "and you agree that you have the right" clause.)

[autism-corner]

oTL

[gaast]

git is a blessing and a curse because on the one hand all of my writing is backed up in a GitHub repo but on the other I almost accidentally lost all the work I did yesterday and in the process deleted literally everything from my cloud storage

[felixcloud6288]

If Tumblr shuts down, we should all move to github. We can make github pages and fork each others' repos as an alternative to reblogging.

[wafflejesus420]

lmao

[rattkinng]

I feel like this is an odd issue to have, but I have a drastically harder time working with and understand GitHub than I do GitLab

[manonamora-if]

Now with a Git Hub Repo!

Makes it easier to report issues. Also create pull requests and whatnot.

Or see in realtime what's being updated.

The 100% Good Twine SugarCube Guide!

NOTE: while the Guide is in its complete form, it will be updated when SugarCube 2 updates (or if I spot a typo/error).

This SugarCube Guide was create as an alternative to the official documentation, providing a comprehensive and wide look over the use of Twine, particularly the SugarCube format.

The Guide is compartmentalised in four categories:

The Basics: or the absolute basics to start with SugarCube No need for extra knowledge. Just the base needed to make something.

The Basics+: adding interactivity, and creating a fully rounded IF game May require a bit of CSS knowledge (formatting rules)

Intermediate Use: adding more customisation and complex code Will probably require some CSS knowledge, and maybe some JavaScript

Advanced More (incomplete): the most complex macros and APIs Will surely require some JavaScript/jQuery knowledge

Each category explains a multitude of aspects of the format, tailored to a specific level of the user. More simpler explanations and examples are available in earlier chapters, compared to the later ones.

If something is unclear, you found a mistake, you would like more examples in the guide, or would like a feature covered, let me know!

The Guide currently covers all macros (as of SugarCube v.2.36.1*), all functions and methods, and APIs. It touches upon the use of HTML, CSS, JavaScript and jQuery, when relevant. It also discusses aspects of accessibility. *In case of format update, this Guide will make relevant edits.

The Guides also provides a list of further resources, for the different coding languages (SugarCube, HTML, CSS, JavaScript, jQuery).

VIEW OR DOWNLOAD THE GUIDE!!!!

[izmirphpdeveloper]

GitHub Deposu Nasıl Silinir?

Merhabalar, bugünkü blog yazımda sizlere GitHub Deposu Nasıl Silinir? adım adım nasıl yapabileceğinizi anlatacağım. GitHub, dünya genelinde en yaygın kullanılan kod geliştirme ve proje yönetimi platformlarından biridir. Ancak, bazen projeler başarısız olabilir veya artık ihtiyacınız olmayabilir ve bu nedenle GitHub deposunu silmek mantıklı bir adım olabilir. Bu yazıda, GitHub deposunu nasıl…